chore(deps): ignore major version bumps in dependabot#195
Merged
Conversation
Major bumps of devDeps (eslint, typescript, prettier) need manual config migration and provide no value for conformance testing. Security updates still come through regardless; scheduled updates are now minor/patch only.
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
ignorerules forversion-update:semver-majoracross all three ecosystems (npm root, npm examples, github-actions).Why: Major bumps of devDeps like eslint, typescript, prettier need manual config migration and provide no value for conformance testing. They also tend to break CI on peer-dep conflicts (e.g. #193 failed because tsdown doesn't support TS 6 yet).
What still happens:
What stops: routine "eslint 9→10" / "typescript 5→6" PRs. We bump majors manually when we decide to.
Closes #193 (superseded by this config change — that PR was failing CI anyway).